-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add C/C++ diff: scope, modules, packages. #37167
Conversation
Co-authored-by: Stefan Karpinski <stefan@karpinski.org>
Thanks. |
Help: Correction needed?Sorry. I think I misunderstood something: Excerpt from docs for context:
An array of paths for using and import statements to consider as project environments or package directories when loading code. It is populated based on the
My issue.My PR said the following:
Though I had not tried it before a few days ago, I thought that was the point of having
It is almost like julia doesn't want us to place our packages under the environment path. QuestionAm I mistaken here? |
The |
Oh. I understand now that I looked into:
|
I suppose this is is probably the best way we could create "conventional" applications in Julia, then: Sample directory tree (root: a "generated" project)
MyApplication/startup.jl:
Command to launch your "conventional" application:
|
Check failing: It now looks like it had nothing to do with me. Should I do a rebase or revert my commits something? |
Would be nice if someone with C++ expertise reviewed this and merged it if it seems good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some minor tweaks
I'm ok with all of your suggestions @vtjnash. |
Yeah, you can do "add suggestion to batch" to all of them in the "files changed" view to easily accept all of them as-written, or copy them locally individually and push the result. But I can also just accept all of them for you and then tag for merging once CI finishes. |
Some of this information would be well suited for a more general (non-c-specific) section.
But from my observations on Discourse:
C/C++ users are particularly confused with the import/using vs include concepts.